home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
IRIX 6.3 Development Libraries
/
SGI IRIX 6.3 Development Libraries.iso
/
dist
/
dist6.3
/
motif_dev.idb
/
usr
/
relnotes
/
motif_dev
/
ch3.z
/
ch3
Wrap
Text File
|
1996-12-06
|
4KB
|
133 lines
- 1 -
3. _C_h_a_n_g_e_s__a_n_d__A_d_d_i_t_i_o_n_s
+o See the _1._2._4-_6._3 _I_R_I_X _I_M _R_e_l_e_a_s_e _N_o_t_e_s, _E_x_e_c_u_t_i_o_n-_O_n_l_y
_E_n_v_i_r_o_n_m_e_n_t for functional changes.
+o _S_e_c_u_r_i_t_y _n_o_t_e: _a_s _i_n _p_r_e_v_i_o_u_s _I_R_I_X _I_M _r_e_l_e_a_s_e_s, _t_h_e
_M_o_t_i_f _d_e_m_o _p_r_o_g_r_a_m_s _a_r_e _s_h_i_p_p_e_d _w_r_i_t_a_b_l_e _b_y _e_v_e_r_y_o_n_e.
_I_f _t_h_i_s _i_s _a _s_e_c_u_r_i_t_y _p_r_o_b_l_e_m _f_o_r _y_o_u, _s_e_t _t_h_e _a_c_c_e_s_s
_t_o _w_h_a_t_e_v_e_r _y_o_u _l_i_k_e _a_f_t_e_r _y_o_u _i_n_s_t_a_l_l _t_h_e _p_r_o_g_r_a_m_s.
+o This release is derived from OSF/Motif 1.2.4, and has
those features.
+o This release is based on X11R6, and has those features.
+o This release builds cleanly (without errors or
warnings) with ANSI C, if you use the flag ----wwwwooooffffffff 111188882222.
That flag suppresses warnings caused by Xt header
files. The warnings are valid, but indicate no
malfunction on a Silicon Graphics system.
+o Tear-off behavior is enabled by setting the
XmNtearOffModel resource to XmTEAR_OFF_ENABLED (the
default is XmTEAR_OFF_DISABLED).
There is no resource converter preregistered for
XmNtearOffModel. To allow tear-off functionality to be
enabled through the resource database, an application
must register its own resource converter for the
XmNtearOffModel resource using the
XmRepTypeInstallTearOffModelConverter function.
The converter is not automatically installed because
many applications use map or cascading callbacks to
dynamically set the sensitivity of items within their
menus. However, if a TearOff Menu is mapped, the
sensitivity of its menu items must be changed
immediately to reflect changes in other application
states. Existing applications are unlikely to change
menu item sensitivity in this manner, so allowing their
menus to be torn off could allow operations to be
enabled at unexpected times. If you activate one of
these menu items, it might crash the application or
cause corruption of persistent data.
A torn-off menu is created in the same visual as the
menu it was torn from. If the original menu was in the
pop-up planes, the torn-off menu is there too. This
means that something that is not really transient is
now in the pop-up planes. It will be subject to all of
the usual problems that non-transient windows in the
- 2 -
pop-up planes face: limited colormap, colormap
flashing, and damage from things that write to the
pop-ups without benefit of a window.
Note that the only bad effects are cosmetic. The
available alternatives include:
- Understand that this is the situation. In
practice, it might not cause a real problem for
you.
- Don't enable tear-off menus if your menus are in
the pop-up planes.
- If your system has overlay planes, put your menus
there instead.
- If your system does not have overlay planes, put
your menus in the normal planes and accept any
redrawing caused by bringing up a menu.